I’ve been googling, reading the documentation and trying different stuff and I can’t find a way to change a service Email integration urgency level to low. RuleSets can do it but they’re about to be phased out and Event Orchestration doesn’t seem to be play nice with email integration.
Coming from OpsGenie it feels like PagerDuty is making simple stuff like this simply impossible or overly complicated.
And no, we don’t have PagerDuty AIOps package.
You can configure your service to change urgency based on incident severity by selecting Dynamic Notifications. Then using an orchestration, you can set the severity (info/warning will make an incident low urgency).
For emails to work with orchestrations, you’d need to send the emails to [integration routing key]@[instance name].pagerduty.com
First off, thank you kind stranger for answering so promptly!
Oh I see, we cannot use a “simple” email integration however we can use the [key of a Pager API v2 integration]@[instance name].pagerduty.com which generate a V2 event which is chewable by the Event Orchestration. It’s a bit disappointing since an email with meaningfulname.service@[instance name].pagerduty.com would make more sense but if works it works!
Many thanks Master McGee! 
Best regards,
Charles D.
Hey no problem, glad it works. One other piece of advice that I give to people in my environment when configuring an email integration: when entering the pagerduty email address into the monitoring tool, put it in the BCC field. It’s very annoying to get additional notifications because someone decided to reply-all to an alert.
